Update programming-languages collection to allow more projects to join#4880
Update programming-languages collection to allow more projects to join#4880jmeridth merged 1 commit intogithub:mainfrom
Conversation
Signed-off-by: Ellie <el@horse64.org>
|
@ell1e I've removed the requirement for signing of commits. That was checked for contributions made via the web UI and I agree, it's a bit ambiguous without DCO involved. We are still reviewing your change, as I think we want to highlight code on GitHub, not on other source code providers. Will let you know soon. |
|
For clarity, I hereby agree to license my suggested contribution, if that one liner even qualifies for any licensing, under whatever license you require. My remark about the signing off wasn't meant to indicate that I disagree with the licensing. |
We tend to follow the
😄 |
(As a side note which for lack of another communication channel I'm putting here, you seem to require
Signed-off-byfor your commits, but seemingly the notices have no info on what that means. You don't seem to be using something like the common "Developer Certificate of Origin" for example. I'd like to point out that at least to me, the sign off seems to be ambiguous and potentially pointless, since I feel like it's not really clear what that means to anybody. If it's to accept the licensing and to certify that I wrote the commit, then perhaps the notices should point that out. However, I could be wrong, I'm not a lawyer.)Please confirm this pull request meets the following requirements:
Which change are you proposing?
Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:
*.png, square, dimensions 288x288, size <= 75 kB)index.md)I'm suggesting that the collection description allow languages that are still actively developed but where their Github presence might be, while up-to-date, secondary and not where issues are tracked.
I'm suggesting this change because:
None of the other collections have the requirement in the description for their Github repository to be the main repository.
This collection already has entries like https://github.com/TinyCC/tinycc that don't fulfill this constraint.
In the light of some recent Github decisions, perhaps projects shouldn't be discouraged from using Github as a secondary presence rather than primary.
Curating a new topic or collection
https://github.com/topics/[NAME]orhttps://github.com/collections/[NAME])*.pngimage (if applicable) andindex.mdindex.mdconform to the Style Guide and API docs: https://github.com/github/explore/tree/main/docsSomething that does not neatly fit into the binary options above